Non-networked device performing certificate authority functions in support of remote AAA

ABSTRACT

In an approach, a certificate authority management device comprises a computing device with an operating system that supports certificate authority software, a power port with shutter door, a first key slot for an administrative user to enable use of the certificate authority management device in response to an insertion of a first key, a second key slot for management of a plurality of hybrid security keys in response to an insertion of a second key, and a touchscreen with graphical user interface.

BACKGROUND

The present invention relates generally to the field of security keysand more particularly to a hybrid security key with isolated physicaland logical attributes for remote Authentication, Authorization, andAuditing (AAA).

Security controls are safeguards or countermeasures to avoid, detect,counteract, or minimize security risks to physical property,information, computer systems, or other assets. A security controlssystem can have a physical layer, e.g. doors and locks, and a technicallayer, e.g. user authentication and logical access controls.

AAA is a term for a framework for intelligently controlling access tocomputer resources, enforcing policies, auditing usage, and providingthe information necessary to bill for services. These combined processesare considered important for effective electronic device management andsecurity.

First, authentication provides a way of identifying a user, typically byhaving the user enter a valid user name and valid password before accessis granted. The process of authentication is based on each user having aunique set of criteria for gaining access. The AAA device compares auser's authentication credentials with other user credentials stored ina database. If the credentials match, the user is granted access to thedevice. If the credentials are at variance, authentication fails anddevice access is denied.

Following authentication, a user must gain authorization for doingcertain tasks. After logging into a device, for instance, the user maytry to issue commands. The authorization process determines whether theuser has the authority to issue such commands. Simply put, authorizationis the process of enforcing policies: determining what types orqualities of activities, resources, or services a user is permitted.Usually, authorization occurs within the context of authentication. Onceyou have authenticated a user, they may be authorized for differenttypes of access or activity.

The final plank in the AAA framework is auditing, which measures theresources a user consumes during access. This can include the amount ofsystem time or the amount of data a user has sent and/or received duringa session. Auditing is carried out by logging of session statistics andusage information and is used for authorization control, billing, trendanalysis, resource utilization, and capacity planning activities.

SUMMARY

Aspects of an embodiment of the present invention disclose a certificateauthority management device. The certificate authority management devicecomprises a computing device with an operating system that supportscertificate authority software, a power port with shutter door, a firstkey slot for an administrative user to enable use of the certificateauthority management device in response to an insertion of a first key,a second key slot for management of a plurality of hybrid security keysin response to an insertion of a second key, and a touchscreen withgraphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a side view of a face with physical attributes of arectangular-shaped hybrid security key, in accordance with an embodimentof the present invention.

FIG. 1B depicts a side view of a face with logical attributes of arectangular-shaped hybrid security key, in accordance with an embodimentof the present invention.

FIG. 1C depicts a side view of the conductive film with a connectedsmart chip embedded in the hybrid security key of FIG. 1B, in accordancewith an embodiment of the present invention.

FIG. 2A depicts a perspective view of a block diagram of components of aCertificate Authority (CA) management device, in accordance with anembodiment of the present invention.

FIG. 2B depicts perspective views of swappable key slots for the keymanagement slot component of FIG. 2A, in accordance with an embodimentof the present invention.

FIG. 2C depicts a block diagram of components of an internal computingdevice suitable for CA management device, in accordance with anembodiment of the present invention.

FIG. 3A depicts a top view of a locking device, in accordance with anembodiment of the present invention.

FIG. 3B depicts a top view of a locking device after key authenticationhas occurred, in accordance with an embodiment of the present invention.

FIG. 3C depicts a front side view of a switch configuration disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention.

FIG. 3D depicts a rear side view of a switch configuration disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention.

FIG. 3E depicts a front side view of a switch interface disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention.

FIG. 3F depicts a rear side view of a switch interface disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention.

FIG. 3G depicts a perspective view of a spacer of the locking device ofFIG. 3A, in accordance with an embodiment of the present invention.

FIG. 3H depicts a perspective view of a lock cylinder of the lockingdevice of FIG. 3A, in accordance with an embodiment of the presentinvention.

FIG. 3I depicts a side view of a first interior wall of lock cylinder ofthe locking device of FIG. 3A, in accordance with an embodiment of thepresent invention.

FIG. 3J depicts a side view of a second interior wall of lock cylinderof the locking device of FIG. 3A, in accordance with an embodiment ofthe present invention.

FIG. 4 depicts a flowchart depicting operational steps of a lockmechanism executing within the locking device of FIGS. 3A-3B, inaccordance with an embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that out of band supportfor authentication, authorization, and auditing (AAA) is significant inapplying security device modification and mitigating communicationattack vectors for non-networked distributed devices. Embodiments of thepresent invention further recognize that there is a lack of ability tosupport the delivery of AAA to distributed devices outside the band ofnetwork or radio frequency (RF) communication.

The problem with securing distributed devices occurs at two layers ofconcern for AAA—the physical layer and the logical layer. At thephysical layer, access to specific distributed devices is generally notcontrolled beyond the use of a physical security control. The ability toperform effective AAA is limited with the use of a physical key. Themanagement of physical keys requires labor intensive manual proceduresto secure key usage, but this does not secure against entitiescircumventing AAA. At the logical layer, devices that rely upon thenormal band of device communication for security services duringcritical operation stages (e.g. a firmware update) can be compromisedvia the communication channel that services as the attack vector. Ifleveraged, this attack vector could impact numerous devices connectedthrough an Internet of Things (IOT) network, a cloud services network, asupervisory control and data acquisition (SCADA) network, and/or aprogrammable logic controller (PLC) system. The inadequate management ofAAA can lead to the unauthorized modification of data resulting in awide range of ramifications from loss of intellectual property,destruction of critical data, destruction of production assets, and lossof life.

Security controls beyond the physical realm, i.e. in the logical layer,have advanced with their adaptability to threats in the virtualizationand consolidation of network operations within a criticalinfrastructure, such as, a cloud services infrastructure and/or an IOTinfrastructure. However, security controls for AAA with out of bandoperations is a critical gap. More precisely, this security controls gapis focused on the physical layer, in which security controls havelargely remained unchanged and rely on systems that are not adaptable toevolving threats. Systems that are not adaptable to evolving threatsallow attack vectors to form that can be manipulated by unauthorizedthird parties. In particular, the management of non-networked deviceslacks physical AAA support during sensitive and vulnerable firmwareoperational cycles, such as a physical upgrade. These attack vectors cancause a loss of Confidentiality, Integrity, and Availability (CIA) ofdata and services in a device or system. CIA are the three criticalattributes or goals of any information security system.

This gap at the physical layer exposes an attack vector that can beleveraged at a subsequent logical security layer. For example, withcritical infrastructure that is controlled with SCADA and supporting PLCsystems, the general assumption suggests that integration of these typesof systems with physical isolation and physical locks is sufficientprotection, but these physical security controls are inadequate becauseof the lack of logical security for devices at the physical layer. Thelack of AAA management at the physical layer leads to the loss of CIA ofcritical data.

Additionally, there are multiple problems with the use of traditionalCertificate Authority (CA) for distributed devices in support of AAA.First, in regards to the technical skills required for CA, the securityand operation of a networked CA is a significant undertaking thatrequires extensive defense with security controls, policies, procedures,and ongoing management to appropriately secure against external threats.Second, the management of AAA for physically remote devices requires asecure yet simplified platform for delivery of CA functions that can beoperated by a layperson.

Thus, embodiments of the present invention recognize that there is aneed for appropriate logical security controls for devices at thephysical layer. Some current systems (e.g. car ignition keys) may or maynot require a physical presence due to support by RF communication, butthis use of a non-physical communication medium introduces anothercommunication channel that exposes an attack vector into the electroniccontrol systems. Currently, no hybrid security key with integratedphysical and logical components exists that is completely dependent uponphysical contact in securing transition between the physical securitylayer and the logical security layer.

In this manner, as discussed in greater detail herein, embodiments ofthe present invention provide the necessary components in an integratedphysical device to support the delivery of AAA to physically distributeddevices outside the band of network or RF communication. Embodiments ofthe present invention further provide a multi-faceted hybrid securitykey that encapsulates physical and logical components to support securemulti-factor AAA through electronic-mechanical operations and physicalhuman-to-machine interaction. Embodiments of the present inventionprovide a solution for securing systems from communication attackvectors by increasing security through the interlinking of physicaloperations with logical operations, assuring the hybrid security key'sorigin through digital signing of a Unique Identification (UID), andremoving external attack vectors by having no RF or networkcommunications.

In multiple embodiments, the hybrid security key with isolated physicaland logical components enables a secure transition between the physicaland logical security layers, logically binds secure credentials withinboth physical and logical layers, supports credentials for remoteauthorization of the hybrid security key's origin, supports secured datadistribution with remote devices, supports secure remote multi-factorauthentication, supports secure remote authorization, supports loggingretention of remote key usage for auditing, uses tamper resistantelectronic components (e.g., zeroisation of contents to fail safe), andenables multiple facets on key shaft to have physical and logicalcontrols. In multiple embodiments, creation and placement of securitycredentials onto the hybrid security key occur at the time ofmanufacture and during the key management lifecycle.

Embodiments of the present invention further recognize that managementand CA functions in support of AAA of devices need to function in aremote capacity without networked devices. In this manner, as discussedin greater detail herein, embodiments of the present invention provide asecure stand-alone (i.e., non-networked) CA device that enables supportfor simplified secure management and use of distributed physical devices(i.e., hybrid security keys and locking devices) in support of AAA.Embodiments of the present invention further provide as the platform forthe management of credentials for both hybrid security keys and lockingdevices during the lifecycle of AAA operations. A self-contained CAdevice mitigates chances for compromise, eliminates the technical careand feeding required for securing the CA, and provides a simplifiedmanagement graphical user interface (GUI) to perform CA functions.

In multiple embodiments, the standalone CA device supports randomasymmetric key pair generations; random seed import and creation; tamperresistant and/or fail safe security controls; cryptography key pairs toenable secure private key storage, secure export of private key, secureprivate key import, and public key export; management of XML AdvancedElectronic Signatures (XAdES); a touch screen with GUI; a physicalbarrier (e.g., a shutter door) that restricts access to power supplyport; a physical barrier (e.g., a shutter door) that restricts access touniversal serial bus (USB) port; restricted access to secure USB port(e.g., only being available during specific operational functions); akeyed slot for programming functions with the hybrid security key;pairing of subsequent external storage devices; differing managementoperations based upon authorized user's role; remote authentication ofhybrid security key's origin; secured data distribution (i.e., readingand writing of data) with authenticated hybrid security keys; secureremote multi-factor authentication of user; secure remote authorizationof user through secure embedded repository—Access Control List (ACL);secured operations with biometric factors (e.g., fingerprint, retinalscan, etc.); secure logging retention of operations for auditing; securelogging retention of operations on authenticated hybrid security key(s);on screen review of AAA activities of user; secure export of loggingfrom distributed devices; key operations for management of the securedlocking device itself; management of multi-faceted hybrid security keysvia swappable key slots; and bonding of CA device component UIDs atpoint of manufacture.

Embodiments of the present invention provide a physical and electroniclocking device that securely encapsulates a physical and logical lock.The lock supports secure multi-factor AAA through various operations(i.e. electro-mechanical, physical hardware circuit modification, andphysical human-to-machine interaction). In multiple embodiments, thelocking device and associated lock mechanism can be used with a matchinghybrid security key that would enable the secure transition fromphysical layer to logical layer. The physical control surface of thehybrid security key would authorize the physical contact of the logicalcontrols on the hybrid security key within the lock. This contact wouldenable the secure transition from physical layer to logical layer anddirect physical connection between the hybrid security key and thecontrol logic within the locking device.

In multiple embodiments, the physical and electronic locking deviceenables secure transition and binding of data between the physical andlogical security layers, supports differing operations based upon anauthorized user's role, supports remote authentication of hybridsecurity key's origin, supports secured data distribution (i.e., readingand writing) with authenticated hybrid security key, supports secureremote multi-factor authentication of user, supports secure remoteauthorization of hybrid security key, supports secured operations withbiometric factors (e.g., fingerprint, retinal scan, etc.), supportssecure logging retention of operations, supports secure loggingretention of operations on authenticated hybrid security key(s),supports key operation for management of locking device itself, supportsmulti-faceted hybrid security keys and alternate axis operations (e.g.,counter clockwise v. clockwise rotation around the axis of hybridsecurity key), supports tamper resistant security controls, supports theretention of key performing unauthenticated or unauthorized operations,and supports hardwire integration with external alarm systems or devicesto notify authorities.

Embodiments of the present invention further provide a mechanism forinitiating and enabling use of the CA device using a hybrid securitykey. The CA device is enabled via a key slot where an authorized usercan insert a hybrid security key and rotate the hybrid security key to afirst detent position. Rotating the hybrid security key to the firstdetent position opens a shutter door to a power port allowing anexternal power supply to be connected to the CA device. Now, the CAdevice can conduct authentication procedures by scanning and validatingthe inserted hybrid security key's authentication code. Once the hybridsecurity key has been authenticated, the CA device allows the hybridsecurity key to be rotated to multiple detent positions of the key slot,in which each detent position enables specific circuitry to completedifferent management functions and/or operational functions (e.g.opening USB shutter door to allow use of USB port).

The present invention will now be described in detail with reference tothe Figures.

In general, hybrid security key 100 consists of a metal keying framewith a bow and at least two-faceted blade with a first side havingphysical attributes and a second side having logical attributes. Inmultiple other embodiments not shown, hybrid security key 100 mayinclude additional faces with physical or logical attributes not shown.For example, hybrid security key 100 may be triangular-shaped with twofaces with logical attributes similar to logical side 120 and one facewith physical attributes similar to physical side 110. In anotherexample, hybrid security key 100 may be square-shaped with two faceswith logical attributes similar to logical side 120 and two faces withphysical attributes similar to physical side 110. Differing hybridsecurity keys with differing number of facets may be used todifferentiate between roles of multiple authorized users and requiredifferent key operations. For example, a two-faceted hybrid security keyis used by an authorized user whose role allows for standard operations,while a three-faceted hybrid security key is used by an authorized userwhose role requires them to complete firmware updates.

FIG. 1A depicts a side view of a face with physical attributes of arectangular-shaped hybrid security key with two faces, in accordancewith an embodiment of the present invention. FIG. 1A provides only anillustration of one embodiment and does not imply any limitations withregard to environments in which different embodiments may beimplemented. In the depicted embodiment, physical side 110 of hybridsecurity key 100 includes authentication code 112, locking pin locations114, and key groove cut 116. In an embodiment, authentication code 112is a physical representation of a key manufacturer's CA signing digitalattributes of the key shaft. The digital attributes of the key shaftconsist of a digital representation of key groove cut 116 combined withthe UID of smart chip 134 (shown in FIG. 1C) and is digitally signed bya private key of the key manufacturer's CA. This enables validation ofthe hybrid security key's origin during AAA processes via decoding withthe key manufacturer's CA public key. In an embodiment, authenticationcode 112 is coupled to the physical surface of physical side 110 as abarcode (e.g. Quick Response (QR) Code). In an embodiment, locking pinlocations 114 represent the locations on hybrid security key 100 thatline up with locking pins of a locking device, such as locking pins 313of locking device 300, in which locking pins 313 fit into a key groovecut of an inserted key, such as key groove cut 116 of hybrid securitykey 100 (see FIG. 3I for locking pins 313). In an embodiment, key groovecut 116 is a physical groove cut into physical side 110 of hybridsecurity key 100 that provides a unique physical locking pin sequence.In several embodiments, key groove cut 116 can be cut into hybridsecurity key 100 by any industry standard.

FIG. 1B depicts a side view of a face with logical attributes of arectangular-shaped hybrid security key with two faces, in accordancewith an embodiment of the present invention. FIG. 1B provides only anillustration of one embodiment and does not imply any limitations withregard to environments in which different embodiments may beimplemented. In the depicted embodiment, logical side 120 of hybridsecurity key 100 includes surface insert 122 and conductive film 124. Inan embodiment, conductive film 124 is coupled to logical side 120 ofhybrid security key 100 with surface insert 122 overlaying conductivefilm 124 (see FIG. 1C below for more details about conductive film 124).In an embodiment, surface insert 122 includes contact points 126 andlocking pin locations 128, in which locking pin locations 128 line upwith locking pin locations 114 on physical side 110 shown in FIG. 1A. Inthe depicted embodiment, contact points 126 are circular-shaped holesthat line up with underlain conductive pads 130 of conductive film 124.In the depicted embodiment, surface insert 122 includes eightcircular-shaped contact points 126 arranged in a line down a centralaxis of surface insert 122. In other embodiments, surface insert 122includes a differing number, shape, and arrangement of contact points126.

FIG. 1C depicts the logical circuitry integrated onto a logical side ofa hybrid security key including conductive film of FIG. 1B and connectedsmart chip, in accordance with an embodiment of the present invention.FIG. 1C provides only an illustration of one embodiment and does notimply any limitations with regard to environments in which differentembodiments may be implemented. In the depicted embodiment, conductivefilm 124 includes conductive pads 130 connected to smart chip 134through conductive traces 132. In the depicted embodiment, conductivefilm 124 includes eight circular-shaped conductive pads 130 arranged ina line down a central axis of conductive film 124. In other embodiments,conductive film 124 includes a differing number, shape, and arrangementof conductive pads 130. In an embodiment, conductive pads 130 are madeof conductive material (e.g. copper). In the depicted embodiment,conductive pads 130 are coupled to the surface of conductive film 124.In the depicted embodiment, conductive pads 130 are connected toconductive traces 132. In an embodiment, conductive traces 132 completecircuitry to connect conductive pads 130 to smart chip 134. In thedepicted embodiment, conductive traces 132 are coupled to the surface ofconductive film 124. In the depicted embodiment, conductive traces 132are connected to conductive pads 130 on a first end and connected tosmart chip 134 on a second end. In the depicted embodiment, smart chip134 is coupled to the surface of conductive film 124. In the depictedembodiment, smart chip 134 is connected to conductive traces 132. In anembodiment, smart chip 134 stores a UID for hybrid security key 100.

FIG. 2A depicts a block diagram of components of a Certificate Authority(CA) management device, in accordance with an embodiment of the presentinvention. FIG. 2A provides only an illustration of one embodiment anddoes not imply any limitations with regard to environments in whichdifferent embodiments may be implemented. In the depicted embodiment, CAmanagement device 200 includes touch screen 210, key management slot220, USB port 230, authorized user key slot 240, power port 250,external lock cable portal 260, biometric input scanner 270, andinternal computing device 280. In an embodiment, CA management device200 is enabled via authorized user key slot 220 when an authorized userinserts a hybrid security key, such as hybrid security key 100, andinitiates CA management device 200. Once CA management device 200 hasbeen activated and AAA has been completed on inserted hybrid securitykey, the hybrid security key may be placed in multiple detent positionsto enable specific circuitry within CA management device 200 to completespecific management functions.

Internal computing device 280 operates as the internal, self-containedcomputer for CA management device 200. In some embodiments, internalcomputing device 280 is a laptop computer, tablet computer, netbookcomputer, personal computer (PC), a desktop computer, a smart phone, orany programmable electronic device or computing system with embeddedoperating system (OS) that supports CA software. At time of manufacture,internal computing device 280 is loaded with an ACL of authorized usersand associated authorizations. Additionally, at time of manufacture,internal computing device 280 is assigned a permanent UID. In anembodiment, internal computing device 280 is electronically paired withother components of CA management device 200 through each UID. In anembodiment, internal computing device 280 stores the UIDs of eachcomponent of CA management device 200 in a UID table (not shown). In anembodiment, the integration of internal computing device 280 in CAmanagement device 200 supports security controls provided by eachcomponent of CA management device 200.

CA software embedded on internal computing device 280 supports CAfunctions, such as cryptographic functions (e.g. Elliptical CurveCryptography (ECC)). CA software embedded on internal computing device280 also supports management of distributed security key and lock sets,management of XAdES, and routines for interactions with an authorizeduser via GUI of touch screen 210. CA software supports management ofdistributed hybrid security keys and locking devices through use ofcryptography public and private key pairs to encrypt and decrypt datapayloads between a hybrid security key, locking device, and a CAmanagement device. At time of manufacture, OS of internal computingdevice 280 is digitally signed with the CA private key. In anembodiment, during OS boot-up, CA private key and UID table are used toconfirm validity of each component and prevent tampering with CAmanagement device 200. In an embodiment, CA management device 200digitally signs data payloads with the CA private key, then lockingdevices of remote CA devices would use a previously distributed andstored CA public key to validate the data payload.

Touch screen 210 with GUI operates to enable an authorized user tointeract with CA management device 200. In an embodiment, touch screen210 is coupled to a top face of CA management device 200. In anembodiment, touch screen 210 is assigned a UID at time of manufacture,which is stored in UID table. In an embodiment, power to touch screen210 is enabled once an inserted hybrid security key in authorized userkey slot 240 has been authenticated and validated by CA software ofinternal computing device 280 for authorization to perform GUIoperations.

Key management slot 220 operates to enable management of dependenthybrid security keys and user AAA operations through swappablemulti-faceted key slots. In an embodiment, key management slot 220 iscoupled to a side face of CA management device 200. In severalembodiments, key management slot 220 includes locking device 300, asdescribed below in FIGS. 3A-3J. In an embodiment, key management slot220 is assigned a UID at time of manufacture, which is stored in UIDtable. In an embodiment, key management slot 220 supports validation ofhybrid security key authentication. In an embodiment, key managementslot 220 allows an authorized user who has enabled CA management device200 through a hybrid security key inserted into authorized user key slot240 to program another hybrid security key inserted into key managementslot 220.

USB port 230 operates with a shutter door to enable a USB connection. Inan embodiment, USB port 230 is coupled to a side face of CA managementdevice 200. In an embodiment, the shutter door of USB port 230 has adefault position of closed. In an embodiment, operation of the shutterdoor of USB port 230 is controlled by the CA software depending on anauthorization or role of a user.

Authorized user key slot 240 operates to allow an authorized user toenable use of CA management device 200. In an embodiment, authorizeduser key slot 240 is coupled to a side face of CA management device 200.In several embodiments, authorized user key slot 240 includes lockingdevice 300, as described below in FIGS. 3A-3J. In an embodiment, at timeof manufacture, authorized user key slot 240 is assigned a UID, which isstored in UID table. In an embodiment, upon insertion of an authorizeduser's hybrid security key, authorized user key slot 220 supportsmultiple detent positions that enable specific circuitry within CAmanagement device 200 to complete specific management functions. Forexample, authorized user key slot 220 with hybrid security key 100inserted and rotated to a first detent position allows the opening ofpower port 250's shutter door.

Power port 250 operates with a shutter door to enable external powersupply connection. In an embodiment, power port 250 is coupled to a sideface of CA management device 200. In an embodiment, the shutter door ofpower port 250 is opened upon successful insertion of a hybrid securitykey into authorized user key slot 240 and rotation to first detentposition. In an embodiment, power port 250 with open shutter door allowsaccess to power port for connection with external power supply. In anembodiment, the shutter door of power port 250 is closed upon removal ofthe hybrid security key from authorized user key slot 240.

External lock cable portal 260 operates to enable attachment of anindustry standard locking cable to physically secure CA managementdevice 200 in place. In an embodiment, external lock cable portal 260 iscoupled to a side face of CA management device 200.

Biometric input scanner 270 operates to allow retinal scanning,fingerprint, and/or facial scanning capabilities. In an embodiment,biometric input scanner 270 is coupled to a top face of CA managementdevice 200 adjacent to touch screen 210. In an embodiment, biometricinput scanner 270 is issued a UID at time of manufacture, which isstored in UID table. In an embodiment, biometric input scanner 270includes a retinal scanner. In another embodiment, biometric inputscanner 270 includes a fingerprint scanner. In another embodiment,biometric input scanner 270 includes a facial scanner. In yet anotherembodiment, biometric input scanner 270 includes a retinal scanner, afingerprint scanner, and/or a facial scanner.

FIG. 2B depicts swappable key slots for the key management slot of FIG.2A, in accordance with an embodiment of the present invention. FIG. 2Bprovides only an illustration of one embodiment and does not imply anylimitations with regard to environments in which different embodimentsmay be implemented. In the depicted embodiment, rectangular key slot222, triangular key slot 224, and square key slot 226 for user key slot220 are shown. In an embodiment, rectangular key slot 222, triangularkey slot 224, and square key slot 226 are interchangeable in keymanagement slot 220 depending on a hybrid security key used. Differingkeys slots allowing for hybrid security keys with differing number offacets may be used to differentiate between roles of multiple authorizedusers and require different key operations.

FIG. 2C is a block diagram depicting components of internal computingdevice 280 suitable for CA management device 200, in accordance with anembodiment of the present invention. FIG. 2C displays internal computingdevice 280, one or more processor(s) 282 (including one or more computerprocessors), communications fabric 281, memory 283, cache 284,persistent storage 285, I/O interfaces 286, display 287, and externaldevices 288. It should be appreciated that FIG. 2C provides only anillustration of one embodiment and does not imply any limitations withregard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.

As depicted, internal computing device 280 operates over communicationsfabric 281, which provides communications between cache 284, computerprocessor(s) 282, memory 283, persistent storage 285, and input/output(I/O) interface(s) 286. Communications fabric 281 may be implementedwith any architecture suitable for passing data and/or controlinformation between processors 282 (e.g. microprocessors, communicationsprocessors, and network processors, etc.), memory 283, external devices288, and any other hardware components within a system. For example,communications fabric 281 may be implemented with one or more buses or acrossbar switch.

Memory 283 and persistent storage 285 are computer readable storagemedia. In the depicted embodiment, memory 283 includes a random accessmemory (RAM). In general, memory 283 may include any suitable volatileor non-volatile implementations of one or more computer readable storagemedia. Cache 284 is a fast memory that enhances the performance ofcomputer processor(s) 282 by holding recently accessed data, and datanear accessed data, from memory 283.

Program instructions for any computer programs may be stored inpersistent storage 285 or in memory 283, or more generally, any computerreadable storage media, for execution by one or more of respectivecomputer processors 282 via cache 284. Persistent storage 285 mayinclude a magnetic hard disk drive. Alternatively, or in addition to amagnetic hard disk drive, persistent storage 285 may include, a solidstate hard disk drive, a semiconductor storage device, read-only memory(ROM), electronically erasable programmable read-only memory (EEPROM),flash memory, or any other computer readable storage media that iscapable of storing program instructions or digital information.

The media used by persistent storage 285 may also be removable. Forexample, a removable hard drive may be used for persistent storage 285.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive, such as via USB shutter door230, for transfer onto another computer readable storage medium that isalso part of persistent storage 285.

I/O interface(s) 286 allows for input and output of data with otherdevices that may operate in conjunction with internal computing device280. For example, I/O interface 286 may provide a connection to externaldevices 288, which may include a keyboard, keypad, a touch screen,and/or some other suitable input devices, such as touch screen 210 asdepicted in FIG. 2A. External devices 288 may also include portablecomputer readable storage media, for example, thumb drives, such as USBport 230. Software and data used to practice embodiments of the presentinvention may be stored on such portable computer readable storage mediaand may be loaded onto persistent storage 285 via I/O interface(s) 286.I/O interface(s) 286 may similarly connect to display 287, such as touchscreen 210 as depicted in FIG. 2A. Display 287 provides a mechanism todisplay data to a user and may be, for example, a computer monitor ortouch screen 210.

FIG. 3A depicts a top view of a locking device, in accordance with anembodiment of the present invention. FIG. 3A provides only anillustration of one embodiment and does not imply any limitations withregard to environments in which different embodiments may beimplemented. In several embodiments, locking device 300 can be a part ofkey management slot 220 and/or authorized user key slot 240. In thedepicted embodiment, locking device 300 contains lock cylinder 310,solenoid valve 320 a, solenoid valve 320 b, and solenoid valve 320 c,barcode scanner 330, spring-loaded interface 340, shaft 350, switchconfiguration disc 360, switch interface disc 370, spacer 380, andspring 390.

In an embodiment, lock cylinder 310 is a cylinder with a key slot on anexposed front face (see FIGS. 3H-J) that is flush with end of lockingdevice 300. In an embodiment, solenoid valve 320 a is coupled to aninterior wall of locking device 300 and located between the interiorwall of locking device 300 and lock cylinder 310. In an embodiment, whenengaged, solenoid valve 320 a extends into lock cylinder 310 to preventrotation of the lock cylinder 310 and/or removal of an inserted hybridsecurity key 100. In an embodiment, solenoid valve 320 b is located inbetween lock cylinder 310 and switch configuration disc 360. In anembodiment, when engaged, solenoid valve 320 b extends to prevent lockcylinder 310 from moving along the central axis of locking device 300.In an embodiment, solenoid valve 320 c is coupled to a rear interiorwall of locking device 300 and located between spacer 380 and the rearwall of locking device 300 with spring 390 spiraling around solenoidvalve 320 c. In an embodiment, solenoid valve 320 c operates as afailsafe circuit breaker when an AAA failure occurs. In an embodiment,solenoid valves 320 a, 320 b, and 320 c are controlled by circuitry oflocking device 300 (not shown).

In an embodiment, barcode scanner 330 is coupled to an interior wall oflocking device 300 and located between the interior wall of lockingdevice 300 and lock cylinder 310. In an embodiment barcode scanner 330operates to scan a barcode of an inserted hybrid security key in lockcylinder 310.

In an embodiment, spring-loaded interface 340 is coupled to an interiorwall of locking device 300 and located between the interior wall oflocking device 300 and lock cylinder 310. In an embodiment,spring-loaded interface 340 operates as a logical interface that, whenapplicable, is engaged against a logical side of an inserted hybridsecurity key, such as logical side 120 of hybrid security key 100 tocomplete a circuit and read information stored on the hybrid securitykey, such as digital attributes of the hybrid security key, credentials,and/or a data payload digitally signed with the CA private key.

In an embodiment, shaft 350 is coupled to a rear exterior face of lockcylinder 310 on one end and can be moved through switch configurationdisc 360, switch interface disc 370, and spacer 380. In an embodiment,switch configuration disc 360 is a disc (see FIGS. 3C-D) located betweenlock cylinder 310 and switch interface disc 370. In an embodiment,switch configuration disc 360 operates to make and break physicalcircuit connections when in physical contact with switch interface disc370 (see FIG. 3B). In an embodiment, switch interface disc 370 is a disc(see FIGS. 3E-F) located between switch configuration disc 360 andspacer 380. In an embodiment, switch interface disc 370 operates to makeand break physical circuit connections when in physical contact withswitch configuration disc 360 (see FIG. 3B). In an embodiment, spacer380 is a disc (see FIG. 3G) with spring 390 coupled to a rear face ofspacer 380 that is located between switch interface disc 370 and a rearinterior wall of locking device 300. In an embodiment, spring 390 is aspring coupled to a rear face of spacer 380 on one end and a rearinterior wall of locking device 300 on a second end.

FIG. 3B depicts a top view of a locking device after key authenticationhas occurred, in accordance with an embodiment of the present invention.FIG. 3B provides only an illustration of one embodiment and does notimply any limitations with regard to environments in which differentembodiments may be implemented. In the depicted embodiment, lockcylinder 310—with a hybrid security key inserted that has passed a firstauthentication step, so solenoid valves have been disengaged (seedecision 405 through decision 430 of FIG. 4)—has been pushed in along acentral axis of locking device 300 to allow shaft 350 to be pushedthrough switch interface disc 370 and spacer 380, and to allow switchconfiguration disc 360 to come in contact with and complete a circuitwith switch interface disc 370.

FIG. 3C depicts a front side view of a switch configuration disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention. FIG. 3C provides only an illustration of oneembodiment and does not imply any limitations with regard toenvironments in which different embodiments may be implemented. In thedepicted embodiment, a front face of switch configuration disc 360includes cam shaft 362, which is a hole through a central axis of switchconfiguration disc 360. In an embodiment, shaft 350 is oriented in camshaft 362 of switch configuration disc 360.

FIG. 3D depicts a rear side view of a switch configuration disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention. FIG. 3D provides only an illustration of oneembodiment and does not imply any limitations with regard toenvironments in which different embodiments may be implemented. In thedepicted embodiment, a rear face of switch configuration disc 360contains conductive elements 361 and cam shaft 362. In an embodiment,conductive elements 361 are pieces of conductive material orientedaround the rear face of switch configuration disc 360. In multipleembodiments, conductive elements 361 can take different shapes and beoriented around switch configuration disc 360 depending on circuitry.

FIG. 3E depicts a front side view of a switch interface disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention. FIG. 3E provides only an illustration of oneembodiment and does not imply any limitations with regard toenvironments in which different embodiments may be implemented. In thedepicted embodiment, front face of switch interface disc 370 containscontact points 371 and hole 373. In an embodiment, contact points 371are made of conductive material to complete a circuit with conductiveelements 361 of switch configuration disc 360. In the depictedembodiment, switch interface disc 370 includes eight circular-shapedcontact points that are arranged around hole 373 in a circular shape. Inother embodiments, switch interface disc 370 includes a differing numberand arrangement of contact points depending on circuitry. In anembodiment in which shaft 350 is oriented through hole 317 (see FIG.3B), the shape of hole 317 prevents switch interface disc 370 from beingrotated.

FIG. 3F depicts a rear side view of a switch interface disc of thelocking device of FIG. 3A, in accordance with an embodiment of thepresent invention. FIG. 3F provides only an illustration of oneembodiment and does not imply any limitations with regard toenvironments in which different embodiments may be implemented. In thedepicted embodiment, rear face of switch interface disc 370 containscontact points 371, wiring 372, and hole 373. In an embodiment, a wireof wiring 372 is coupled to each contact point 371 on switch interfacedisc 370. In the depicted embodiment, wiring 372 includes eight wiresthat are individually coupled to each contact point 371. In otherembodiments, switch interface disc 370 includes differing number ofwires depending on how many contact points are included.

FIG. 3G depicts a perspective view of a spacer of the locking device ofFIG. 3A, in accordance with an embodiment of the present invention. FIG.3G provides only an illustration of one embodiment and does not implyany limitations with regard to environments in which differentembodiments may be implemented. In the depicted embodiment, spacer 380contains pin sockets 381 and cam shaft 382. In an embodiment, pinsockets 381 are arranged around the perimeter of spacer 380. Pin sockets381 operate to allow pins or solenoid valves to be engaged in pinsockets 381 to prevent spacer 380 and switch configuration disc 360connected through shaft 350 from being rotated.

FIG. 3H depicts a perspective view of a lock cylinder of the lockingdevice of FIG. 3A, in accordance with an embodiment of the presentinvention. FIG. 3H provides only an illustration of one embodiment anddoes not imply any limitations with regard to environments in whichdifferent embodiments may be implemented. In the depicted embodiment,lock cylinder 310 includes front face 319 with rectangular slot 311,which is an internal cut out through the central axis of lock cylinder310, and back face 318 with hole 317, which is a hole into rear face 318for solenoid valve 320 b.

FIG. 3I depicts a side view of an interior wall of lock cylinder of thelocking device of FIG. 3A that corresponds with a face of a hybridsecurity key with physical aspects, such as physical side 110 of hybridsecurity key 100, in accordance with an embodiment of the presentinvention. FIG. 3I provides only an illustration of one embodiment anddoes not imply any limitations with regard to environments in whichdifferent embodiments may be implemented. In the depicted embodiment,interior wall 312 of lock cylinder 310 contains locking pins 312 andopening 314. In an embodiment, eight locking pins are coupled to anexposed face of interior wall 312. Other embodiments may contain adiffering number of locking pins. In an embodiment, locking pins 313 aremoveable up and down along a straight line track and project out fromthe exposed face of the interior wall. In an embodiment, opening 314 isa cutout or opening through the lock cylinder to allow the barcodescanner of the locking device to scan the barcode on a physical side ofa hybrid security key. For example, opening 314 is a cut through lockcylinder 310 to allow barcode scanner 330 to scan authentication code112 on physical side 110 of hybrid security key 100.

FIG. 3J depicts a side view of an interior wall of lock cylinder of thelocking device of FIG. 3A that corresponds with a face of a hybridsecurity key with logical aspects, such as logical side 120 of hybridsecurity key 100, in accordance with an embodiment of the presentinvention. FIG. 3J provides only an illustration of one embodiment anddoes not imply any limitations with regard to environments in whichdifferent embodiments may be implemented. In the depicted embodiment,interior wall 315 contains interface door 316. In an embodiment,interface door 316 is a moveable door on a track that when a track keypin is engaged, interface door 316 is rotated open along the trackwithin the lock cylinder (not shown).

FIG. 4 depicts a flowchart depicting operational steps of a lockmechanism executing within locking device 300 of FIGS. 3A-3B, inaccordance with an embodiment of the present invention. In the depictedembodiment, lock mechanism 400 operates to complete AAA on a hybridsecurity key inserted into a locking device of a CA management device.It should be appreciated that the process depicted in FIG. 4 illustratesone possible iteration of lock mechanism, which repeats for each time ahybrid security key, such as hybrid security key 100, is inserted into alocking device, such as locking device 300, of a CA device, such as CAmanagement device 200.

In decision 405, once a hybrid security key has been inserted into alocking device of a CA device, locking mechanism 400 determines whethera key groove cut of the hybrid security key arranges locking pins in alock cylinder of locking device in correct arrangement to enablerotation of lock cylinder. For example, once hybrid security key 100 hasbeen inserted into authorized user key slot 240 of CA management device200, locking mechanism 400 determines whether key groove cut 116 onphysical side 110 of hybrid security key 100 arranges locking pins 313of interior wall 312 of lock cylinder 310 in correct arrangement toenable rotation of lock cylinder. If, in decision 405, key groove cut116 does arrange locking pins 313 in correct arrangement to enablerotation of lock cylinder, then locking mechanism 400 moves to step 415.If, in decision 405, key groove cut 116 does not arrange locking pins313 in correct arrangement to enable rotation of lock cylinder, thenlocking mechanism 400 moves to step 410, in which authentication failureprocedures occur.

In step 410, because an authentication failure has occurred, lockingmechanism 400 engages a solenoid value to prevent the removal of ahybrid security key for a predetermined length of time to allow forauditing to occur. For example, locking mechanism 400 engages solenoidvalues 320 to prevent the removal of hybrid security key 100 for apredetermined length of time to allow for auditing to occur. In anembodiment, locking mechanism 400 completes auditing by extracting thecredentials of the inserted hybrid security key (e.g., hybrid securitykey 100. In an embodiment, in step 410, locking mechanism 400 sets offan authentication failure alarm. In embodiments where applicable,locking mechanism 400 disengages spring-loaded interface 340 and closesinterface door 116. In embodiments where applicable, locking mechanism400 engages solenoid valve 320 b behind lock cylinder 110 to pushcylinder back to position in FIG. 3A and engages solenoid valve 320 aback into lock cylinder to prevent rotation and removal of hybridsecurity key 100.

In step 415, locking mechanism 400 allows a barcode scanner to scan abarcode of the inserted hybrid security key. For example, lockingmechanism 400 allows barcode scanner 330 to scan authentication code 112on physical side 110 of hybrid security key 100. In an embodiment,locking mechanism 400 uses a public CA key stored in the locking deviceto validate digital representation of key groove cut digitally signedwith CA private key. For example, locking mechanism 400 uses public CAkey stored in locking device 300.

In decision 420, locking mechanism 400 determines whether the digitalrepresentation of the key groove cut stored in the barcode matches thedigital representation stored in the locking device using the public CAkey. For example, locking mechanism 400 determines whether the digitalrepresentation of key groove cut 116 stored in authentication code 112matches the digital representation stored in locking device 300 usingthe public CA key. If, in decision 420, locking mechanism 400 determinesthat the digital representation of key groove cut 116 stored inauthentication code 112 matches the digital representation stored in thelocking device using the public CA key, then locking mechanism 400 movesto step 425. If, in decision 420, locking mechanism 400 determines thatthe digital representation of key groove cut 116 stored inauthentication code 112 does not match the digital representation storedin the locking device using the public CA key, then locking mechanism400 moves to step 410, in which authentication failure procedures occur.

In step 425, locking mechanism 400 disengages a solenoid valve extendedinto the lock cylinder and flashes an external indicator on the lockingdevice indicating to a user who inserted the hybrid security key torotate the hybrid security key in a specified direction (e.g. left orright). For example, locking mechanism 400 disengages solenoid valve 320a extended into lock cylinder 310 (see FIG. 3A) and flashes externalindicator on locking device 300 (not shown) indicating to a user whoinserted hybrid security key 100 to rotate hybrid security key 100 in aspecified direction (e.g. left or right). For example, locking mechanism400 flashes an arrow pointing to the left or to the right.

In decision 430, locking mechanism 400 determines whether the userrotated a hybrid security key (e.g. hybrid security key 100) in thespecified direction. If, in decision 430, the user rotated hybridsecurity key 100 in the specified direction, then locking mechanism 400moves to step 435. If, in decision 430, the user did not rotate hybridsecurity key 100 in the specified direction, then locking mechanism 400moves to step 410, in which authentication failure procedures occur.

In step 435, locking mechanism 400 enables the user to rotate the hybridsecurity key inserted in the lock cylinder to a detent position and pushin along the central axis of the locking device. For example, lockingmechanism 400 enables the user to rotate hybrid security key 100inserted in lock cylinder 310 to a detent position and push in along thecentral axis of locking device 300 (see FIG. 3B). In an embodiment, thedetent position correlates with an activity user is proposedly trying tocomplete using CA management device 200. In an embodiment, as lockcylinder 310 is pushed in, locking mechanism 400 engages track key pinof interface door 316 to rotate interface door 316 open to exposelogical side 120 of hybrid security key 100.

In step 440, locking mechanism 400 engages a spring-loaded interfaceoutside of the lock cylinder to come in physical contact with a logicalside of the hybrid security key. For example, locking mechanism 400engages spring-loaded interface 340 to come in physical contact withlogical side 120 of hybrid security key 100. In an embodiment, lockingmechanism 400 uses public CA key stored in the locking device tovalidate UID of the hybrid security key stored in its smart chip. Forexample, locking mechanism 400 uses public CA key stored in lockingdevice 300 to validate UID of hybrid security key 100 stored in smartchip 134.

In decision 445, locking mechanism 400 determines whether the barcode onthe physical side of the hybrid security key matches the UID stored inthe smart chip on the logical side of the hybrid security key. Forexample, locking mechanism 400 determines whether authentication code112 of physical side 110 matches UID stored in smart chip 134 of logicalside 120. In an embodiment, locking mechanism 400 uses the CA public keystored in locking device 300 to decrypt authentication code 112 and usethe retrieved UID stored in smart chip 134 to validate both the physicaland logical attributes on hybrid security key 100 as being authentic.If, in decision 445, locking mechanism 400 determines thatauthentication code 112 matches UID stored in smart chip 134 of logicalside 120, then locking mechanism moves to step 450, in whichauthentication success procedures occur. If, in decision 445, lockingmechanism 400 determines that authentication code 112 does not match UIDstored in smart chip 134 of logical side 120, then locking mechanismmoves to step 410, in which authentication failure procedures occur.

In step 450, locking mechanism 400 completes authentication successprocedures and auditing procedures. In an embodiment, locking mechanism400 completes auditing by extracting the credentials of hybrid securitykey 100, digitally signing a data payload (e.g., an ACL fordistribution, a firmware update, logging data, etc.) with private key ofCA management device 200, and writing signed data payload to securelogging storage of locking device 300 and to secure logging storage ofhybrid security key 100. In an embodiment, once auditing is completed,locking mechanism moves onto authorization steps.

In step 455, locking mechanism 400 begins authorization procedures byreviewing the extracted credentials from the hybrid security key tocompare with an ACL stored on an internal computing device of the CAdevice to see what the user with that hybrid security key is authorizedto do on the CA device. For example, locking mechanism 400 reviews theextracted credentials from hybrid security key 100 to compare with ACLstored on internal computing device 280 of CA management device 200 tosee what the user with hybrid security key 100 is authorized to do on CAmanagement device 200.

In decision 460, locking mechanism 400 determines whether, based on ACL,user is authorized. If, in decision 460, locking mechanism 400determines that, based on ACL, user is authorized, then lockingmechanism 400 moves to step 465. If, in decision 460, locking mechanism400 determines that, based on ACL, user is not authorized, then lockingmechanism 400 moves to step 470, in which authorization alarm isactivated.

In step 465, locking mechanism 400 disengages pins or solenoid valves(not shown) from pin sockets 381 around perimeter of spacer 380. In anembodiment, once solenoid valves are disengaged, spacer 380 and switchconfiguration disc 360—which are connected by cam shafts along shaft350—can be rotated to complete circuitry between switch configurationdisc 360 and switch interface disc 370 to enable a certain activity andits associated circuitry to be completed on CA management device 200. Inan embodiment, decision 445 through decision 460 are repeated after apredetermined length of time to revalidate the authorization of theuser.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of apparatuses (systems)and methods according to embodiments of the invention. It will beunderstood that each block of the flowchart illustrations and/or blockdiagrams, and combinations of blocks in the flowchart illustrationsand/or block diagrams, can be implemented by the apparatuses describedabove.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems and methods according to various embodiments of the presentinvention. In this regard, each block in the flowchart or block diagramsmay represent a module, segment, or portion of instructions, whichcomprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the blocks may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

What is claimed is:
 1. A standalone secure non-networked device thatperforms certificate authority, the standalone secure non-networkeddevice comprising: a computing device with an operating system and withembedded certificate authority software; a first key slot for anadministrative user to activate the standalone secure non-networkeddevice and enable the certificate authority software in response to aninsertion of a first hybrid security key by extracting credentials froma smart chip of the first hybrid security key and comparing theextracted credentials to an access control list stored on the computingdevice to determine an authorization of the first hybrid security key;and a second key slot to manage a plurality of hybrid security keys inresponse to an insertion of a respective hybrid security key of theplurality of hybrid security keys, wherein: the second key slot is oneof a plurality of swappable key slots that each have a different shapedkey slot that allow use with respective ones of the plurality of hybridsecurity keys having at least one logical face and at least one physicalface, the at least one logical face comprises a smart chip, and the atleast one logical face and the at least one physical face are separatefaces of each respective hybrid security key of the plurality of hybridsecurity keys.
 2. The standalone secure non-networked device of claim 1,further comprising a USB port with a shutter door.
 3. The standalonesecure non-networked device of claim 1, further comprising a biometricinput scanner.
 4. The standalone secure non-networked device of claim 3,wherein the biometric input scanner is selected from the groupconsisting of: a retinal scanner, fingerprint scanner, and facialscanner.
 5. The standalone secure non-networked device of claim 1,wherein a repository of the computing device contains an access controllist of authorized users and associated authorizations of eachauthorized user.
 6. The standalone secure non-networked device of claim1, wherein the first key slot comprises a first locking device with afirst lock cylinder that matches with the first hybrid security key. 7.The standalone secure non-networked device of claim 1, wherein thesecond key slot comprises a second locking device with a second lockcylinder that allows use with a rectangular-shaped hybrid security keywith one physical face and one logical face.
 8. The standalone securenon-networked device of claim 1, wherein the second key slot can beswapped for a third key slot comprising a third locking device with athird lock cylinder that allows use with a triangular-shaped hybridsecurity key with at least one physical face and at least one logicalface.
 9. The standalone secure non-networked device of claim 1, whereinthe second key slot can be swapped for a fourth key slot comprising afourth locking device with a fourth lock cylinder that allows use with asquare-shaped hybrid security key with two physical faces and twological faces.
 10. The standalone secure non-networked device of claim1, further comprising a power port with shutter door.
 11. The standalonesecure non-networked device of claim 1, further comprising a touchscreenwith a graphical user interface.
 12. The standalone secure non-networkeddevice of claim 1, wherein each component of the standalone securenon-networked device is assigned a permanent unique identification at atime of manufacture, and wherein the permanent unique identification foreach component of the standalone secure non-networked device is storedin a table in a repository of the computing device.
 13. The standalonesecure non-networked device of claim 12, wherein the computing device iselectronically coupled to each component of the standalone securenon-networked device through each respective permanent uniqueidentification.
 14. The standalone secure non-networked device of claim1, wherein the operating system of the computing device is digitallysigned with a private certificate authority key of a certificateauthority key pair.
 15. The standalone secure non-networked device ofclaim 1, wherein the first key slot can be turned using the first hybridsecurity key to one of a plurality of detent positions, wherein each ofthe plurality of detent positions enables a respective set of functionsof the certificate authority software.
 16. The standalone securenon-networked device of claim 1, wherein the first hybrid security keycomprises: at least one physical face on a first side of the firsthybrid security key comprising a key groove cut and a barcode coupled toa top surface of the physical face; and at least one logical face on asecond side of the first hybrid security key comprising a surface insertoverlaying a conductive film, wherein the conductive film includes atleast one contact point, at least one conductive trace, and a smartchip.
 17. The standalone secure non-networked device of claim 1, whereinthe second hybrid security key comprises: at least one physical face ona first side of the second hybrid security key comprising a key groovecut and a barcode coupled to a top surface of the physical face; and atleast one logical face on a second side of the second hybrid securitykey comprising a surface insert overlaying a conductive film, whereinthe conductive film includes at least one contact point, at least oneconductive trace, and a smart chip.